[SPARK-32448][K8S][TESTS] Use single version for exec-maven-plugin/scalatest-maven-plugin#29248
[SPARK-32448][K8S][TESTS] Use single version for exec-maven-plugin/scalatest-maven-plugin#29248dongjoon-hyun wants to merge 1 commit intoapache:masterfrom dongjoon-hyun:SPARK-32448
Conversation
…alatest-maven-plugin
| <exec-maven-plugin.version>1.4.0</exec-maven-plugin.version> | ||
| <extraScalaTestArgs></extraScalaTestArgs> | ||
| <kubernetes-client.version>4.9.2</kubernetes-client.version> | ||
| <scala-maven-plugin.version>3.2.2</scala-maven-plugin.version> |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Actually, this PR's change passed Jenkins K8s IT because it triggers all tests successfully. The one test case failure is irrelevant and flaky one. |
|
Retest this please. |
| <artifactId>spark-kubernetes-integration-tests_2.12</artifactId> | ||
| <properties> | ||
| <download-maven-plugin.version>1.3.0</download-maven-plugin.version> | ||
| <exec-maven-plugin.version>1.4.0</exec-maven-plugin.version> |
| <extraScalaTestArgs></extraScalaTestArgs> | ||
| <kubernetes-client.version>4.9.2</kubernetes-client.version> | ||
| <scala-maven-plugin.version>3.2.2</scala-maven-plugin.version> | ||
| <scalatest-maven-plugin.version>1.0</scalatest-maven-plugin.version> |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
|
Hi, @liyinan926 . Could you review this K8s IT dependency change PR? This PR upgrades the old versions and refactors them in order to avoid being outdate again. |
|
Retest this please. |
|
Hi, @HyukjinKwon and @viirya . Could you review this PR? This is simply in order to update the dependency by removing the duplications. And, it's tested already but it's retriggered due to the flakiness in K8s minikube installation in Jenkins. |
|
Thank you so much, @HyukjinKwon . |
|
Oh, Thank you, @viirya , too! |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
For a record, the following is the K8s |
…alatest-maven-plugin ### What changes were proposed in this pull request? Two different versions are used for the same artifacts, `exec-maven-plugin` and `scalatest-maven-plugin`. This PR aims to use the same versions for `exec-maven-plugin` and `scalatest-maven-plugin`. In addition, this PR removes `scala-maven-plugin.version` from `K8s` integration suite because it's unused. ### Why are the changes needed? This will prevent the mistake which upgrades only one place and forgets the others. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the Jenkins K8S IT. Closes #29248 from dongjoon-hyun/SPARK-32448. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit 13c64c2) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
|
Test build #126585 has finished for PR 29248 at commit
|
|
Test build #126590 has finished for PR 29248 at commit
|
|
Test build #126600 has finished for PR 29248 at commit
|
What changes were proposed in this pull request?
Two different versions are used for the same artifacts,
exec-maven-pluginandscalatest-maven-plugin. This PR aims to use the same versions forexec-maven-pluginandscalatest-maven-plugin. In addition, this PR removesscala-maven-plugin.versionfromK8sintegration suite because it's unused.Why are the changes needed?
This will prevent the mistake which upgrades only one place and forgets the others.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the Jenkins K8S IT.